|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation calls for a valid SHA1 as specified in the reference.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3174
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[FIPS 180-1] "Secure Hash Standard", United States of American,/
National Institute of Science and Technology, Federal/
Information Processing Standard (FIPS) 180-1, April/
1993./
/
[MD4] "The MD4 Message Digest Algorithm," Advances in/
Cryptology - CRYPTO '90 Proceedings, Springer-Verlag,/
1991, pp. 303-311./
/
[RFC 1320] Rivest, R., "The MD4 Message-Digest Algorithm", RFC/
1320, April 1992./
/
[RFC 1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC/
1321, April 1992./
/
[RFC 1750] Eastlake, D., Crocker, S. and J. Schiller, "Randomness/
Requirements for Security", RFC 1750, December 1994./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
